Skip to content

{ai}[foss/2023b] PyTorch v2.2.1#22361

Open
Flamefire wants to merge 3 commits into
easybuilders:developfrom
Flamefire:20250221140101_new_pr_PyTorch221
Open

{ai}[foss/2023b] PyTorch v2.2.1#22361
Flamefire wants to merge 3 commits into
easybuilders:developfrom
Flamefire:20250221140101_new_pr_PyTorch221

Conversation

@Flamefire
Copy link
Copy Markdown
Contributor

@Flamefire Flamefire commented Feb 21, 2025

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 21, 2025

Diff of new easyconfig(s) against existing ones is too long for a GitHub comment. Use --review-pr (and --review-pr-filter / --review-pr-max) locally.

@boegel
Copy link
Copy Markdown
Member

boegel commented Feb 26, 2025

@boegelbot please test @ jsc-zen3
EB_ARGS="--include-easyblocks-from-pr 3633"

@boegelbot
Copy link
Copy Markdown
Collaborator

@boegel: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de

PR test command 'if [[ develop != 'develop' ]]; then EB_BRANCH=develop ./easybuild_develop.sh 2> /dev/null 1>&2; EB_PREFIX=/home/boegelbot/easybuild/develop source init_env_easybuild_develop.sh; fi; EB_PR=22361 EB_ARGS="--include-easyblocks-from-pr 3633" EB_CONTAINER= EB_REPO=easybuild-easyconfigs EB_BRANCH=develop /opt/software/slurm/bin/sbatch --job-name test_PR_22361 --ntasks=8 ~/boegelbot/eb_from_pr_upload_jsc-zen3.sh' executed!

  • exit code: 0
  • output:
Submitted batch job 5791

Test results coming soon (I hope)...

Details

- notification for comment with ID 2684269442 processed

Message to humans: this is just bookkeeping information for me,
it is of no use to you (unless you think I have a bug, which I don't).

@boegelbot
Copy link
Copy Markdown
Collaborator

Test report by @boegelbot
Using easyblocks from PR(s) easybuilders/easybuild-easyblocks#3633
FAILED
Build succeeded for 0 out of 1 (1 easyconfigs in total)
jsczen3c1.int.jsc-zen3.fz-juelich.de - Linux Rocky Linux 9.5, x86_64, AMD EPYC-Milan Processor (zen3), Python 3.9.21
See https://gist.github.com/boegelbot/3673dab5f88a9a9ce509c5a8d105627a for a full test report.

@Flamefire Flamefire force-pushed the 20250221140101_new_pr_PyTorch221 branch from 9b30e45 to 6a4dcb2 Compare March 21, 2025 12:36
@Flamefire Flamefire closed this Apr 1, 2025
@Flamefire Flamefire deleted the 20250221140101_new_pr_PyTorch221 branch April 1, 2025 11:02
@Flamefire Flamefire restored the 20250221140101_new_pr_PyTorch221 branch April 1, 2025 11:02
@Flamefire Flamefire reopened this Apr 1, 2025
@Flamefire
Copy link
Copy Markdown
Contributor Author

We have 2.3.0 for 2023b. Shall we abandon this?

@Thyre Thyre added the 2023b label Aug 18, 2025
…2.2.1_no-cuda-stubs-rpath.patch, PyTorch-2.2.1_fix-test_extension_backend-without-vectorization.patch
@Flamefire Flamefire force-pushed the 20250221140101_new_pr_PyTorch221 branch 3 times, most recently from 60dca97 to 6a1905f Compare April 16, 2026 10:55
@Flamefire Flamefire force-pushed the 20250221140101_new_pr_PyTorch221 branch from 6a1905f to 3e1e631 Compare April 16, 2026 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants